• The most recent PTFs are listed at the top of this table.
• The Navigator for i PTFs are shipped in the HTTP group. It is recommended that you use the latest group PTF and also keep current on related PTF groups listed here:

• See also the list of Installed Product requirements.
• Follow these Steps for applying PTFs

3. Apply or remove the PTFs (immediate mode).                             
                                                                             
4. Start the ADMIN1 job with this command:                            

> STRTCPSVR SERVER(*IAS) INSTANCE(ADMIN1)                                            

5. Refresh (or reload) your browser after you apply the IBM Navigator for i PTFs.  

Note: Navigator is built with cache-busting options so that every new build requires the browser to reload resources.  Navigator also turns off caching.  Browsers however determine whether or not these options are respected.  When a new PTF is applied, clearing the browser cache is not required as long as the browser is respecting these options.  If you are not seeing the new build date (check Home > About) or see anything that is unexpected, clearing cache may be the best option to get you on your way to using the new Navigator code.  

• A good time to refresh your browser is before you log in, on the login panel.  Select the Reload or Refresh icon on your browser before you log in:
• 
• Q4 2023 PTF had some incompatibilities that may require some users to open a new browser window or open an incognito or private browser window for the first log in after applying the PTF.

Configure GUI Logs for Trace-level (FINEST) debug:

#configureLogs

 

To configure the GUI log file, go to Serviceability > Configure GUI Logs.

1. Select Navigator GUI Log Level: FINEST (Trace)
2. By default all the components will be selected.  This is too much data!  Do not leave All selected!  Deselect the top checkbox (to unselect all), and then select the requested components:  Work Management, Monitors, AS400, TLS, etc.
3. Click Save
4. Recreate your issue
5. Save the messages.log file to send in or run the admin collector

 

 

This will now enhance the console.log file generated for browser debugging as well.  To collect this browser console.log file, see How to Generate a console.log file for IBM Navigator for i. 

 

To set these values without the GUI (if support is requesting a log file to debug an issue with Navigator), edit the file /qibm/userdata/os/admininst/admin1/wlp/usr/servers/admin1/jvm.options and add these 2 lines (modifying the list of components as requested):

-Dcom.ibm.navigator.logging.level=FINEST
-Dcom.ibm.navigator.logging.trace.components=AS400,TLS,SQL,Authorization,DBConn

 

Using "All" is not recommended because there is too much data collected creating large files.  The options for debugging are listed here:

AJS, ARE, AsyncComServer, AS400, Auth, Basic, Class, CMOD, Command, Common, Config&Service, Controller, Core, Crypto, CustomCharts, Dashboard, DBConn, Debugger, Dispatch, EIM, FileSystem, FUID, Home, IDS, IFS, IOCHandler, LDAP, Monitors, MRI, MyWork, NAS, Network, PDI, PDISQL, Printer, Regex, Security, Serviceability, SQL, SSO, Swap, System, TLS, Toolkit, Users, Util, WebAdmin, WorkManagement

 

---

 

Configure GUI Logs for Trace-level (FINEST) debug:

#toolboxTrace

 

To turn on the IBM Java toolbox trace, go to Serviceability > Configure GUI Logs.

1. Turn on Java Toolbox Tracing
2. Set the name for the Java Toolbox Tracing File. Give it a unique name so that it does not append to an existing file. By default it is stored in /QIBM/UserData/OS/AdminInst/admin1/wlp/usr/servers/admin1/logs/
3. Click Save
4. Recreate your issue
5. Save the javaToolboxTraceXXX.txt file to send in or run the admin collector